After Time Machine finishes backing up my iMac, the words "Cleaning Up" are displayed below the scroll bar that depicts how much of the event has finished. Sometimes this "Cleaning Up" takes several minutes (up to 30 minutes), while other times, it's done after only a few seconds. What is going on behind the scenes when Time Machine is Cleaning Up?
iMac, OS X El Capitan (10.11.6), iMac (24-inch, Early 2009)
Finishing Backup orCleaning Up
This is usually done at the end of each backup, but if the Preparing phase determines there isn't enough room for the new backup, it will be done first.
- •On every backup, Time Machine deletes any "expired" backups:
- •Any backup over 24 hours old, keeping only the first backup of each day.
- •Any of those "daily" backups over 30 days old, keeping only the first of the week.
- (Unless it's out of room, Time Machine will only delete 5 expired backups at a time.)
- •If there isn't enough room for the new backup, Time Machine will delete any expired backups first; if that doesn't make enough space, it will then delete the oldest backup(s).
These deletions can be fairly quick, or may take quite a while, depending on how many items are involved. And, the slower the connection to them, the longer it will take -- so if you're backing-up wirelessly, it will take much longer than to an external drive connected by FireWire.
Each deletion is documented in the system.log. You can see or monitor these via the Consoleapplication or via the widget insection #A1.
If you see a message saying "Found partially deleted backup; trying again to delete," the named backup may be damaged -- Time Machine probably tried to delete it earlier, but couldn't. If you see the same one on repeated backups, try deleting it via the Finder. If that doesn't work, try repairingyour backups, per item #A5.
Unless it's out of space, you can cancel a backup in this phase without causing a problem -- Time Machine will "catch up" the necessary deletions on subsequent backups. Cancelling one that's out of room won't cause a serious problem, but it does mean no backup can be made.
(On Snow Leopard or Leopard, when Time Machine is out of room for backups made over a network, this can be extremely slow. Time Machine must "compact" the sparse bundle after each deletion. It's even worse if a "deep traversal" is required, as that is also performed after each one.)
along with backing up it indexes so it could be building or cleaning or attending to those indexes. If the program is not throwing up an error it's probably alight, but if your drive is filling up, on the verge of failing or if you are doing a backup over the network expect additional latency.
BDAqua:
That makes perfect sense. I thought that maybe the system was being
optimized as happened back in the day after any software had been installed.
Given that each back up is quite large (as a whole or what was changed
between sessions), I can see that Time Machine was simply making room for
this latest back up session. Thinking back, given what was changed between
sessions, the newest back up would be bigger that the space left on the
disk. My connection to the external drive (destination) is USB, so it's
fairly quick. Firewire is not an option as this MacBook did not come
equipped with a Firewire port (too bad for me).
Thanks,
alan
On Wed, Sep 7, 2016 at 9:44 AM, Apple Support Communities Updates <
Glad I cou;d help Alan. 🙂
time machine
